home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
programs
/
150tips.zip
/
MSGS.ZIP
/
MISSED.MSG
< prev
next >
Wrap
Text File
|
1993-05-12
|
3KB
|
59 lines
Date: 05-10-93 (09:27) Number: 62758 of 63372 (Refer# 62660)
To: BART SABATELLI
From: DAVID TERRY
Subj: time stamping
Read: NO Status: PUBLIC MESSAGE
Conf: BETA (6) Read Type: MAIL FROM YOU (R/O) (+)
-> 05-09-93 (07:49) (1) RONALD STEPP Off Normally
-> **************************************************************
-> NO CONNECT / NO CARRIER
-> **************************************************************
-> NO CONNECT / NO CARRIER
-> **************************************************************
-> Carrier Lost ...
-> **************************************************************
-> Carrier Lost ...
-> **************************************************************
-> 05-09-93 (17:28) (1) MICHAEL REEVES (14400E) (A) WAUSAU,WI.
The above extra messages appear when you tell PCBoard to "Monitor Missed
Connections".
The first two examples at the top indicate that a RING DETECT occcured but that
your modem responded "NO CARRIER" before a "CONNECT" message ever occured.
In other words, if the caller used a modem to dial into your system, the
handshaking process NEVER COMPLETED to the point of "connecting" the caller.
The second two messages indicate that a CONNECTION was established by the
caller (so a modem must have been used) but that the caller lost carrier
(decided to hang up, or there was too much line noise and the modem hung up)
prior to logging into the system.
-> 1) were 4 different calls lost
Lost? No... missed would be a little more accurate. The phone rang 4 times,
yes, but in two cases a connection was never established and in two more cases
the caller never logged in before losing carrier.
-> 2) would the time spacing look like two-callers
-> 3) was it the next caller (Michael Reeves) that actually made it on his 5th
-> call?
You cannot make that assumption.
-> Everything else in the callers log is stamped well, this should be too.
You can do that if you want. Just edit your PCBTEXT file and add @systime@ in
front of the "Lost Carrier" and "NO CONNECT" messages.
Here is a sample batch file you could use to perform the change:
MKPCBTXT C:\PCB\GEN\PCBTEXT /I:34 "@systime@ NO CONNECT/@optext@"
MKPCBTXT C:\PCB\GEN\PCBTEXT /I:215 "@systime@ Carrier Lost..."
NOTE: the systime and optext variables must be in uppercase. Also, C:\PCB\GEN
may not be the proper location for your pcbtext file. Adjust the batch file as
necessary for your system.